Ride chaining

ABSTRACT

A system for determining a dispatch includes an input interface, a processor, and an output interface. The input interface is to receive a request for a first pickup including a first pickup location and a first destination. The processor is configured to determining a driver to dispatch to the first pickup location. The output interface is to provide a first pickup indication to the driver to go to the first pickup location. The input interface is further to receive a first pickup arrival indication indicating the driver arrived at the first pickup location. The output interface is further to provide a first destination indication indicating to the driver to go to the first destination. The input interface is further to receive a request for a second pickup including a second pickup location and a second destination.

CROSS REFERENCE TO OTHER APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/027,727 entitled COMBINING RIDES IN A RIDE SHARING SYSTEM filedJul. 22, 2014 which is incorporated herein by reference for allpurposes.

BACKGROUND OF THE INVENTION

A ride sharing system connects drivers who wish to share their vehicleswith riders looking for a ride. Matching an individual rider with anindividual driver gets the rider to his destination quickly. However,driver capacity is not used efficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating an embodiment of a system forride chaining.

FIG. 2 is a block diagram illustrating an embodiment of a driverdispatch server system.

FIG. 3 is a block diagram illustrating an embodiment of a driverselection system.

FIG. 4 is a diagram illustrating an embodiment of route for a drivermaking a single pick up and dropoff.

FIG. 5 is a diagram illustrating an embodiment of a route for a drivermaking two pickups and two dropoffs combined into a single route.

FIG. 6 is a diagram illustrating an embodiment of a chained route for adriver, adding a third pickup and dropoff to a route already comprisingtwo pickups and two dropoffs.

FIG. 7 is a diagram illustrating a chained route for a driver, adding asecond pickup and dropoff to a route comprising a single pickup anddropoff.

FIG. 8A is a flow diagram illustrating an embodiment of a process for adispatch.

FIG. 8B is a flow diagram illustrating an embodiment of a process forreceiving a request for a second pickup during a dispatch.

FIG. 9 is a flow diagram illustrating an embodiment of a process fordetermining a driver to dispatch to a pickup location.

FIG. 10 is a flow diagram illustrating an embodiment of a process fordetermining a detour time.

FIG. 11 is a flow diagram illustrating an embodiment of a process fordetermining a most efficient new route comprising a current route with aride added.

FIG. 12 is a flow diagram illustrating an embodiment of a rider process.

FIG. 13 is a flow diagram illustrating an embodiment of a driverprocess.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Ride chaining is disclosed. A system for determining a dispatchcomprises an input interface for receiving a request for a first pickupincluding a first pickup location and a first destination, a driverselection system for determining a driver to dispatch to the firstpickup location, and an output interface for providing a first pickupindication to the driver to go to the first pickup location; wherein theinput interface is further for receiving a first pickup arrivalindication indicating the driver arrived at the first pickup location,wherein the output interface is further for providing a firstdestination indication indicating to the driver to go to the firstdestination; and wherein the input interface is further for receiving arequest for a second pickup including a second pickup location and asecond destination.

In some embodiments, a system for coordinating ride sharing between aset of drivers and a set of riders includes a driver system associatedwith each driver (e.g., a smartphone or other processing andcommunications device), a rider system associated with each rider (e.g.,a smartphone or other processing and communications device), and adriver dispatch server system for dispatching drivers to give rides toriders. A rider uses the rider system to request a ride, the driverdispatch server system assigns the ride to a driver, the ride request isdelivered to the driver using the driver system, and the driver drivesto meet the rider and gives them the ride. In some embodiments, drivercapacity can be used more efficiently by sharing rides. If two ridersrequest similar rides (e.g., with similar start points and end points)or rides that overlap significantly at points closely in time, the ridecan be shared. If both requests are received by the driver dispatchserver system within a predetermined window of time, the driver dispatchserver system determines that the rides should be shared, determines thecorrect order of stops (e.g., pick up passenger 1, pick up passenger 2,drop off passenger 2, drop off passenger 1), and provides the route tothe driver. If a driver has already been assigned a route by the driverdispatch server system, and a request for a new ride is received by thedriver dispatch server system that can be shared with the alreadyassigned route, the driver dispatch server system modifies the route toinclude the new ride, and provides the new modified route to the driver.In some embodiments, the current destination of the driver can bemodified to include the new route (e.g., where the driver is driving towhen the new ride is added to the driver route). In some embodiments,any destination on the driver route after the current destination can bemodified (e.g., a destination of the driver is not modified while thedriver is on the way to the destination).

In some embodiments, when a rider starts the ride share app, he isinitially given a choice of requesting an individual ride or a sharedride. In the event the rider selects an individual ride, a driver isimmediately requested to pick up the rider. The rider typicallycommunicates a destination to the driver directly rather than throughthe app. When the driver indicates that the ride is complete, a chargefor the ride is determined (e.g., based on distance traveled and ontime), and the rider is charged. In some embodiments, in the event therider selects a shared ride, the rider is prompted for a destinationaddress. The server uses the destination address to determine whether aride can be combined. In some embodiments, the server determines atypical charge for the ride based at least in part on the pickup anddestination addresses, applies a ride sharing discount to the charge,and provides the discounted charge amount to the rider, so the riderknows how much the ride will cost. In some embodiments, a ride sharingdiscount comprises a fixed amount (e.g., the price is reduced by 25%).In some embodiments, a ride sharing discount is determined based atleast in part on the likelihood of finding a matching rider to share theride with. In some embodiments, a rider requesting a shared ride isprompted for a party size (e.g., number of passengers) in order toensure that there will be room in the car for another rider to share theride.

In some embodiments, the server attempts to match the rider with anotherrider to share the ride. In the event there is already a rider with asimilar ride waiting to share, the server matches the new rider with thewaiting rider and dispatches a driver. In the event there is not alreadya rider with a similar ride waiting, the rider waits until another riderwith a similar ride requests a shared ride. In some embodiments, theserver determines whether two requested rides are similar enough to becombined by estimating a time for the desired rides for the first riderand second rider individually (e.g., taking separate individual rides)and for the combined ride for each rider (e.g., the time for the firstrider pickup to the first rider dropoff and the second rider pickup tothe second rider dropoff) and determining that it is appropriate tocombine the rides in the event that combining the rides slows them downby less than a slowdown threshold (e.g., 5%, 10%, 5 minutes, etc.). Insome embodiments, the slowdown threshold can vary (e.g., by location,time of day, passenger mood, etc.). In some embodiments, differentpassengers can have different slowdown thresholds for accepting acombined ride. In some embodiments, the system has a predeterminedtime-out threshold for the shared ride waiting time (e.g., the riderwaits no more than 10 minutes to locate another rider). In someembodiments, the rider is provided with a waiting estimate based ontypical ride request statistics. In some embodiments, in the event thewaiting estimate is above a threshold (e.g., the time-out threshold oranother threshold), the rider is informed that the chance of finding ashared ride is too unlikely and is returned to the individual riderequest section of the app. If no rider is found to share the ridewithin the time-out threshold, the rider is given an individual ride. Insome embodiments, the rider is charged the shared ride price regardlessof whether a rider is found to share the ride with. In some embodiments,in the event no rider is found to share the ride with, the rider ischarged the full price. In some embodiments, when the driver arrives topick up a rider as part of a shared ride, the rider has a time limit(e.g., 1 minute) to meet the driver (e.g., to prevent the other rider ofthe shared ride from waiting too long). In some embodiments, in theevent the rider misses the time limit, he is still charged for his ridefor inconveniencing the driver and the other rider. In some embodiments,in the event that the ride for the first rider and the ride for thesecond rider overlap by only a small amount, the ride sharing discountis reduced or eliminated (e.g., the riders are charged full price). Insome embodiments, ride sharing includes three riders sharing a singleride. In some embodiments, ride sharing is limited to a vehicle'smaximum seating capacity (e.g., passenger seats available, back seatsavailable, etc.).

In some embodiments, trip efficiency is increased by dynamicallyselecting pickup and dropoff locations (e.g., dropping off the firstpassenger a block away from their destination in order to avoid thedriver looping around the block or making a left turn onto a busystreet; selecting a pickup point at a major intersection between bothriders and instructing them to walk there, etc.).

In various embodiments, a system for ride chaining updates a pool ofriders desiring rides in the event that an indication is received that arider desires a ride, in the event that a rider indicates that a riderno longer desires a ride, a rider rejects a driver assigned to provide aride, a rider accepts a driver assigned to a ride, a pickup locationchange, a dropoff location change, or any other appropriate indication.In some embodiments, a system for ride chaining updates a pool ofpotential drivers in the event that a new driver indicates availabilityto provide a ride, a driver indicates an available seat due to anupcoming drop-off, a driver indicates one less seat available due to apickup, a driver indicates unavailability to provide a ride, a driveraccepts a potential rider, a driver rejects a potential rider, a driverchanges route (e.g., as indicated by position information received froma device location—for example, a GPS location signal indicating avehicle location), a driver indicates a dropoff location change, apickup location change, or any other appropriate event for updating apool of potential drivers. In some embodiments, a system for ridechaining recalculates a selection of a driver for a rider based on anupdated pool of riders and/or an updated pool of drivers.

FIG. 1 is a block diagram illustrating an embodiment of a system forride chaining. In the example shown, FIG. 1 comprises network 100. Invarious embodiments, network 100 comprises one or more of the following:a local area network, a wide area network, a wired network, a wirelessnetwork, the Internet, an intranet, a storage area network, a cellularnetwork, or any other appropriate communication network. Rider system102 and driver system 104 comprise user systems (e.g., computing systemsfor operation by users). In some embodiments, one or more of ridersystem 102 and driver system 104 comprises a system accessed by a userdirectly (e.g., the user is in proximity with the user system). In someembodiments, one or more of user system 102 and user system 104comprises a system accessed by a user remotely (e.g., the user is not inproximity with the user system, and accesses the user system via network100 and a separate user system). In the example shown, rider system 102and driver system 104 comprise mobile devices (e.g., smartphones, tabletcomputers, etc.). Rider system 102 and driver system 104 comprisesystems accessing driver dispatch server system 106 (e.g., accessingdriver dispatch server system 106 via network 100). In variousembodiments, there are 2, 5, 22, 122, 4320, 26100, or any otherappropriate number of user systems (e.g., rider systems and driversystems) accessing driver dispatch server system 106. Driver dispatchserver system 106 comprises a system for managing drivers giving ridesto riders. In some embodiments, driver dispatch server system 106comprises a system for connecting a rider and a driver. In someembodiments, driver dispatch server system 106 comprises a system fordetermining a driver to assign a ride to. In some embodiments, driverdispatch server system 106 comprises a system for assigning multiplerides to a driver. In various embodiments, driver dispatch server system106 comprises a computer, a computer with multiple processors, multiplecomputers connected via a local network, multiple computers connectedvia a wide area network, multiple computers connected via the Internet,multiple computers connected via network 100, or any other appropriatecomputing system or systems. In some embodiments, a processor of driverdispatch server system 106 is coupled with a memory for storinginstructions to perform processes as described herein. In variousembodiments, the processors comprising rider system 102, driver system104, and driver dispatch server system 106 comprise any one of a varietyof proprietary or commercially available single or multi-processorsystems (e.g., an Intel™-based processor) or other type of commerciallyavailable processor able to support communications in accordance witheach particular embodiment and application.

FIG. 2 is a block diagram illustrating an embodiment of a driverdispatch server system. In some embodiments, driver dispatch serversystem 200 comprises driver dispatch server system 106 of FIG. 1. In theexample shown, driver dispatch server system 200 comprises inputinterface 202. In some embodiments, input interface 202 comprises aninput interface for receiving information via a network (e.g., a wired,wireless, internet, cell phone or other communication network enablingcommunication from a rider system or a driver system). In variousembodiments, input interface 202 comprises an input interface forreceiving a request for a pickup including a first pickup location and afirst destination, for receiving a first pickup arrival indicationindicating a driver arrived at the first pickup location, receiving arequest for a second pickup including a second pickup location and asecond destination, or for receiving any other appropriate information.In some embodiments, input interface 202 is implemented using aprocessor. Driver dispatch server system 200 additionally comprisesoutput interface 204. In some embodiments, output interface 204comprises an output interface for providing information via a network(e.g., a wired, wireless, internet, cell phone or other communicationnetwork enabling communication to a rider system or a driver system). Invarious embodiments, output interface 204 comprises an output interfacefor providing a first pickup indication to a driver to go to a firstpickup location, for providing a first destination indication indicatingto the driver to go to the first destination, or for providing any otherappropriate information. In some embodiments, output interface 204 isimplemented using a processor. Driver selection system 206 comprises adriver selection system for selecting a driver. In some embodiments,driver selection system 206 selects a driver to assign to a ride basedon a ride criteria. In some embodiments, driver selection systemreceives a ride request (e.g., via input interface 202) and determines adriver to assign the ride. In some embodiments, driver selection system206 determines a driver for ride chaining (e.g., assigning a ride to adriver that is in the process of carrying out a route including one ormore rides). In various embodiments, driver selection system 206determines a driver based at least in part on a detour criterion, apickup delay criterion, a distance criterion, or any other appropriatecriteria. In some embodiments, driver selection system 206 isimplemented using a processor. In various embodiments, the elements ofdriver dispatch server system 200 are implemented all on a singleprocessor, each on an individual processor, or shared among multipleprocessors in any appropriate way. In some embodiments, driver selectionsystem 206 monitors existing en route rides being driven by drivers todetermine potential rides that a new ride request can be combined with.

FIG. 3 is a block diagram illustrating an embodiment of a driverselection system. In some embodiments, driver selection system 300implements driver selection system 206 of FIG. 2. In the example shown,driver selector comprises a selector for selecting a driver. In someembodiments, driver selector 302 comprises a selector for selecting adriver from driver database 304. Driver database 304 comprises adatabase of driver information. In various embodiments, driverinformation comprises driver name, driver vehicle type, driver vehiclecapacity, driver present location, driver assigned route, or any otherappropriate information. Driver selector 302 additionally uses routetime information determined by route time calculator 306 for determininga driver. Route time calculator comprises a calculator for determining(e.g., estimating) a time for a proposed route for a driver. In someembodiments, route time calculator determines a detour time incurred byadding a new rider to an existing route for a driver. Memory 308 iscoupled with driver selector 302 and route time calculator 306 andstores and provides instructions to driver selector 302 and/or routetime calculator 306.

In some embodiments, driver database 304 is updated with a newrider—driver assignment and new route configuration—for example, the newrider(s) and new route for the driver are stored in driver database 304.In some embodiments, a next rider request for a ride is evaluated usingupdated driver database 304. In some embodiments, existing requests fora ride are re-evaluated using updated driver database 304.

FIG. 4 is a diagram illustrating an embodiment of route for a drivermaking a single pick up and dropoff. The diagram of FIG. 4 additionallyshows communications between the driver and a driver dispatch serversystem. In some embodiments, the driver comprises a driver using adriver system (e.g., driver system 104 of FIG. 1) in communication witha driver dispatch server system (e.g., driver dispatch server system 106of FIG. 1). In the example shown, driver paths between locations aredrawn with solid lines and driver communications are drawn with dashedlines. The driver starts at driver initial location 400. When the driveris at driver initial location 400, a pickup indication is received(e.g., from the driver dispatch server system). The pickup indicationcomprises a passenger pickup location. A route is determined for thedriver and first passenger pickup location 402 is provided to the driver(e.g., determined from the first pickup indication). The driver thendrives to passenger pickup location 402. At passenger pickup location402, a pickup arrival indication is provided and a destinationindication is received. In some embodiments, the destination indicationis received concurrently with the pickup indication. In someembodiments, the destination indication comprises a passengerdestination. In some embodiments, the destination indication comprisesan indication to drive to the passenger destination. The driveradditionally picks up one or more passengers at passenger pickuplocation 402. The driver then drives to passenger dropoff location 404.The driver provides a destination arrival indication and drops off theone or more passengers. The route is then complete.

FIG. 5 is a diagram illustrating an embodiment of a route for a drivermaking two pickups and two dropoffs combined into a single route. Thediagram of FIG. 5 shows communications between the driver and a driverdispatch server system. In some embodiments, the driver comprises adriver using a driver system (e.g., driver system 104 of FIG. 1) incommunication with a driver dispatch server system (e.g., driverdispatch server system 106 of FIG. 1). In the example shown, driverpaths between locations are drawn with solid lines and drivercommunications are drawn with dashed lines. The driver starts at driverinitial location 500. When the driver is at driver initial location 500,a first pickup indication and a second pickup indication are received. Aroute is determined for the driver and first passenger pickup location502 is provided to the driver (e.g., determined from the first pickupindication). The driver then drives to first passenger pickup location502. When the driver arrives at first passenger pickup location 502, afirst pickup arrival indication is provided, and a first destinationindication is received. The first destination indication comprises thedestination associated with the first passenger pickup location. In someembodiments, the first destination indication is received concurrentlywith the first pickup indication. The driver additionally picks up oneor more passengers at first passenger pickup location 502. In someembodiments, the driver confirms that passengers were picked up at firstpassenger pickup location 502. In some embodiments, the driver confirmsthe number of passengers picked up at first passenger pickup location502 (e.g., indicates the number of passengers picked up at firstpassenger pickup location 502, receives an indication of an expectednumber of passengers and confirms that that number of passengers werepicked up at first passenger pickup location 502, etc.). In someembodiments, in the event that the number of passengers to pick up isgreater than the expected number of passengers (e.g., in the event thata rider called for a ride for one person but has three friends heexpects to take with him) the driver refuses to take the party on theride and the first ride is cancelled (e.g., because the driver hasadditionally agreed to take a second group of passengers together withthe first group and will not have enough room with the unexpected largergroup). Second passenger pickup location 504 is then provided to thedriver (e.g., determined from the second pickup indication). The driverthen drives to second passenger pickup location 504. At second passengerpickup location 504 a second pickup arrival indication is provided and asecond destination indication is received. In some embodiments, thesecond destination indication is received concurrently with the secondpickup indication. The driver additionally picks up one or morepassengers at second passenger pickup location 504. In some embodiments,the driver confirms that passengers were picked up at second passengerpickup location 504. In some embodiments, the driver confirms the numberof passengers picked up at second passenger pickup location 504. Firstpassenger dropoff location 506 is then provided to the driver (e.g.,determined from the first destination indication). The driver thendrives to first passenger dropoff location 506. A first destinationarrival indication is provided. The driver additionally drops off theone or more passengers picked up at first passenger pickup location 502.In some embodiments, the driver confirms that the one or more passengerspicked up at first passenger pickup location 502 were dropped off.Second passenger dropoff location 508 is then provided to the driver(e.g., determined from the second destination indication). The driverthen drives to second passenger dropoff location 508. A seconddestination arrival indication is provided. The driver additionallydrops off the one or more passengers picked up at second passengerpickup location 504. In some embodiments, the driver confirms that theone or more passengers picked up at second passenger pickup location 504were dropped off. The route is then complete. In some embodiments, thesecond passenger dropoff location precedes the first passenger dropofflocation in the route and the second set of passengers is dropped offprior to the first set of passengers and the indication for seconddestination arrival and the indication for first destination arrival areprovided appropriately.

FIG. 6 is a diagram illustrating an embodiment of a chained route for adriver, adding a third pickup and dropoff to a route already comprisingtwo pickups and two dropoffs. In some embodiments, the route of FIG. 6comprises the route of FIG. 5 with a third passenger pickup and dropoffadded after the route has started. The diagram of FIG. 6 additionallyshows communications between the driver and a driver dispatch serversystem. Only communications additional to the communications of FIG. 5are shown (e.g., each communication that is shown in FIG. 5 additionallyoccurs during the route of FIG. 6 but is not shown). In someembodiments, the driver comprises a driver using a driver system (e.g.,driver system 104 of FIG. 1) in communication with a driver dispatchserver system (e.g., driver dispatch server system 106 of FIG. 1). Inthe example shown, driver paths between locations are drawn with solidlines and driver communications are drawn with dashed lines. The driverstarts at driver initial location 600. As the driver proceeds to firstpassenger pickup location 602, a third pickup indication is received.After the driver reaches first passenger pickup location 602 and picksup passengers, the driver is provided with third passenger pickuplocation 604. In some embodiments, the driver system determines that thepickup associated with the third pickup indication should happen priorto the pickup associated with the second pickup indication. The driverthen drives to third passenger pickup location 604. When the driverarrives at third passenger pickup location 604, a third pickup arrivalindication is provided, and a third destination indication is received.The third destination indication comprises the destination associatedwith the third passenger pickup location. In some embodiments, the thirddestination indication is received concurrently with the third pickupindication. The driver additionally picks up one or more passengers atthird passenger pickup location 604. In some embodiments, the driverconfirms that passengers were picked up at third passenger pickuplocation 604. In some embodiments, the driver confirms the number ofpassengers picked up at third passenger pickup location 604 (e.g.,indicates the number of passengers picked up at third passenger pickuplocation 604, receives an indication of an expected number of passengersand confirms that that number of passengers were picked up at thirdpassenger pickup location 604, etc.). The driver then proceeds to pickup passengers at second passenger pickup location 606 and drop offpassengers at first passenger dropoff location 608. The driver is thenprovided with third passenger dropoff location 610 (e.g., scheduledbefore second passenger dropoff location 612 by the driver system). Thedriver drives to third passenger dropoff location 610 and drops off theone or more passengers picked up at third passenger pickup location 604.A third destination arrival indication is provided. The driver proceedsto drop off passengers at second passenger dropoff location 612, and theroute is complete.

In various embodiments, an additional passenger pickup is added for aroute with only one passenger pickup, with two passenger pickup, withthree passenger pickup, with four passenger pickup, or any other numberof passenger pickups. In various embodiments, the order of the pickupsand drop-offs is any combination or permutation of the pickups ordrop-offs.

FIG. 7 is a diagram illustrating a chained route for a driver, adding asecond pickup and dropoff to a route comprising a single pickup anddropoff. The diagram of FIG. 7 additionally shows communications betweenthe driver and a driver dispatch server system. In some embodiments, thedriver comprises a driver using a driver system (e.g., driver system 104of FIG. 1) in communication with a driver dispatch server system (e.g.,driver dispatch server system 106 of FIG. 1). In the example shown,driver paths between locations are drawn with solid lines and drivercommunications are drawn with dashed lines. The driver starts at driverinitial location 700. When the driver is at driver initial location 700,a first pickup indication is received (e.g., from the driver dispatchserver system). The first pickup indication comprises a passenger pickuplocation. A route is determined for the driver and first passengerpickup location 702 is provided to the driver (e.g., determined from thefirst pickup indication). The driver drives to first passenger pickuplocation 702. At first passenger pickup location 702, the driverprovides a first pickup arrival indication and receives a firstdestination indication. In some embodiments, the first destinationindication is received concurrently with the first pickup indication.The driver additionally picks up one or more passengers at firstpassenger pickup location 702. The driver then drives to first passengerdropoff location 704. While driving to first passenger dropoff location704, the driver receives a second pickup indication. After reachingfirst passenger dropoff location 704, a destination arrival indicationis provided and the one or more passengers are dropped off. Secondpassenger pickup location 706 is then provided to the driver (e.g.,determined from the second pickup indication). The driver drives tosecond passenger pickup location 706. At second passenger pickuplocation 706, the driver provides a second pickup arrival indication andreceives a second destination indication. In some embodiments, thesecond destination indication is received concurrently with the secondpickup indication. The driver additionally picks up one or morepassengers at second passenger pickup location 706. The driver thendrives to second passenger dropoff location 708. After reaching secondpassenger dropoff location 708, a second destination arrival indicationis provided and the one or more passengers picked up at second passengerpickup location 706 are dropped off. The route is then complete.

In some embodiments, rides are chained as in FIG. 7 and/or are alsointertwined similar to FIG. 5 and FIG. 6 in a continuing sequence. Insome embodiments, a driver receives a new passenger pickup during anypart of a current route (e.g., when en route to a pickup, when en routeto a dropoff, etc.).

In some embodiments, the system tracks a set of drivers about to dropoffa passenger to see whether any incoming requests for a ride can matchfor a ride chaining as in FIG. 7.

FIG. 8A is a flow diagram illustrating an embodiment of a process for adispatch. In some embodiments, the process of FIG. 8A is executed bydriver dispatch server system 106 of FIG. 1. In the example shown, in800, a request for a first pickup including a first pickup location anda first destination is received. In 802, a driver is determined todispatch to the first pickup location. In some embodiments, the drivercomprises a driver that is already driving (e.g., a driver that will beclosest to the pickup location at the soonest). In some embodiments, thedriver comprises a driver that is not already driving (e.g., a driverthat is closest to the pickup location). In 804, a first pickupindication is provided to the driver to go to the first pickup location.In 806, a first pickup arrival indication indicating the driver hasarrived at the first pickup location is received. In 808, a firstdestination indication indicating to the driver to go to the firstdestination is received. In 810, a first destination arrival indicationindicating the driver has arrived at the first destination is received.

FIG. 8B is a flow diagram illustrating an embodiment of a process forreceiving a request for a second pickup during a dispatch. In someembodiments, the process of FIG. 8B is executed by driver dispatchserver system 106 of FIG. 1. In some embodiments, the process of FIG. 8Boccurs concurrently with the process of FIG. 8A. In the example shown,in 850, a request for a second pickup including a second pickup locationand a second destination is received. In various embodiments, theprocess of FIG. 8B occurs prior to 800 of FIG. 8A, after 800 of FIG. 8A,after 802 of FIG. 8A, after 804 of FIG. 8A, after 806 of FIG. 8A, after808 of FIG. 8A, or at any other appropriate time.

FIG. 9 is a flow diagram illustrating an embodiment of a process fordetermining a driver to dispatch to a pickup location. In someembodiments, the process of FIG. 9 implements 802 of FIG. 8. In someembodiments, the process of FIG. 9 comprises a process for determining adriver to assign a ride to (e.g., a ride requested by a rider using arider system). In the example shown, in 900, the next driver is selectedfrom the set of drivers with routes (e.g., drivers that have alreadybeen assigned routes by the driver dispatch server system). In someembodiments, the next driver comprises the first driver. In 902, thedetour time (e.g., the amount of time by which adding the ride extendsthe route) and pickup delay (e.g., the delay until the ride passenger ispicked up) are determined to add the ride to the driver route (e.g., theroute assigned to the selected driver). In 904, it is determined ifthere are more drivers with routes. In the event it is determined thatthere are more drivers with routes, control passes to 900. In the eventit is determined that there are no more drivers with routes, controlpasses to 906. In 906, it is determined whether a driver from the set ofdrivers with routes meets delay criteria. In various embodiments, thedelay criteria comprises a limit on the detour time (e.g., extending theride by a factor of 1.3, extending the ride by 15 minutes, etc.), thedelay criteria comprises a limit on pickup delay (e.g., 5 minutes, 10minutes, etc.), the delay criteria comprises a limit on both detour timeand pickup delay (e.g., a limit on the sum of the detour time and thepickup delay, a limit on the product of the detour time and the pickupdelay, etc.), or the delay criteria comprises any other appropriatecriteria. In the event it is determined that a driver from the set ofdrivers with routes meets the delay criteria, control passes to 908. In908, the ride is assigned to the driver with a route with minimum delaytime (e.g., detour time, pickup delay, a combination of detour time andpickup delay, etc.). The process then ends. In the event it isdetermined in 906 that a driver from the set of drivers with routes doesnot meet the delay criteria, control passes to 910. In 910, the ride isassigned to the closest driver without a ride (e.g., the driver withouta ride with minimum pickup delay).

FIG. 10 is a flow diagram illustrating an embodiment of a process fordetermining a detour time. In some embodiments, the process of FIG. 10implements determining a detour time (e.g., determining a detour time asin 902 of FIG. 9). In some embodiments, determining a detour timecomprises determining an amount of time that adding a ride extends aroute. In the example shown, in 1000, a projected time for a currentroute is determined (e.g., using a route time calculator—for example,route time calculator 306 of FIG. 3). In 1002, the most efficient newroute comprising the current route with the ride added is determined. In1004, the projected time for the most efficient new route is determined.In 1006, the detour time is determined. In some embodiments, the detourtime comprises the difference in the projected time for the mostefficient new route and the projected time for the current route.

FIG. 11 is a flow diagram illustrating an embodiment of a process fordetermining a most efficient new route comprising a current route with aride added. In some embodiments, the process of FIG. 11 implements 1002of FIG. 10. In the example shown, in 1100, the route segment for pickup(e.g., the segment of the route in which the pickup location of the rideshould be added) is determined. In some embodiments, the route segmentfor pickup is determined by determining the route segment closest to thepickup location. In some embodiments, the route segment for pickup isdetermined by determining a first route location closest to the pickuplocation and selecting the route segment connecting to the first routelocation with an opposite route location closer to the route segment forpickup. In 1102, the pickup location is inserted between the endpointsof the route segment for pickup. In 1104, the route segment for thedestination is determined. In 1106, the destination location is insertedbetween the endpoints of the route segment for the destination.

FIG. 12 is a flow diagram illustrating an embodiment of a rider process.In some embodiments, the process of FIG. 12 is executed by a rider usinga rider system (e.g., rider system 102 of FIG. 1). In the example shown,in 1200, the rider indicates to request a ride. In 1202, the riderreceives a route user interface (e.g., a user interface for indicating aroute). In 1204, the rider indicates a pickup location (e.g., using theuser interface). In 1206, the rider indicates a destination location(e.g., using the user interface). In 1208, the rider receives a requestto share the ride (e.g., a request to indicate whether sharing the ridewith other passengers is acceptable). In some embodiments, a riderreceives a ride discount in the event that the ride is shared. In 1210,sharing acceptability is indicated. In 1212, the rider receives a rideassignment (e.g., from a driver dispatch server system). In 1214, therider receives a ride pickup (e.g., a driver arrives and picks the riderup). In 1216, the rider takes the ride. In some embodiments, the ride isshared with other riders (e.g., when the passenger was picked up otherriders were already in the vehicle, or during the course of the rideother riders were picked up). In 1218, the rider receives a ride dropoff(e.g., the destination is reached and the rider is dropped off). In1220, the rider rates the driver (e.g., indicates to the driver dispatchserver system a rating of the driver quality). In 1222, the rider ratesother riders (e.g., other riders the ride was shared with).

FIG. 13 is a flow diagram illustrating an embodiment of a driverprocess. In some embodiments, the process of FIG. 13 is executed by adriver using a driver system (e.g., driver system 104 of FIG. 1). In theexample shown, in 1300, the driver qualifies to drive a chained ride. Invarious embodiments, in order to driver a chained ride, the driver isrequired to log a certain number of driving hours, pass a test, achievea certain customer rating, or qualify in any other appropriate way. In1302, an indication of a pickup location is received. In 1304, thedriver drives to the pickup location. In 1306, the driver picks up oneor more passengers. In 1308, the driver confirms the group size (e.g.,the driver receives an indication indicating the group size and confirmsthat the number of passengers picked up matches the group size). In someembodiments, in the event that the group size is incorrect, the driverturns the passengers away. In 1310, the driver receives an indication ofa next location (e.g., a next location to drive to). In 1312, the driverdetermines whether the next location comprises a pickup location or adestination location. In the event the next destination comprises apickup location, control passes to 1304. In the event the next locationcomprises a destination location, control passes to 1314. In 1314, thedriver drives to the destination location. In 1316, the driver drops offone or more passengers. In 1318, the driver indicates that passengersdropped off. In 1320, the driver receives an indication indicating anext location or that the route is complete. In 1322, it is determinedwhether the indication comprises a route complete indication. In theevent the indication comprises a next location, control passes to 1312.In the event the indication comprises a route complete indication,control passes to 1324. In 1324, the driver rates the passengers (e.g.,the passengers driven on the route).

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system, comprising: an input interface of acomputer configured to receive a ride sharing acceptability indication;a processor in communication with the input interface, the processorconfigured to determine a vehicle to dispatch to the first pickuplocation for a first ride upon a verification of the ride sharingacceptability indication; an output interface in communication with theprocessor and configured to provide a first pickup indication to adriver device of the vehicle, wherein the first pickup indicationindicates to the driver to go to the first pickup location; the inputinterface configured to receive a request for a second ride; theprocessor configured to share at least a first portion of the first ridewith at least a second portion of the second ride; and the processorconfigured to provide a second pickup indication to the driver device,the second pickup indication modifying a route from the first pickupindication for the driver device.
 2. The system according to claim 1,wherein the vehicle is not associated with a ride from the system priorto the first ride.
 3. The system according to claim 1, wherein thevehicle is associated with a ride from the system prior to the firstride.
 4. The system according to claim 1, wherein the input interface isconfigured to receive the request for the second ride prior to a requestfor the first ride.
 5. The system according to claim 1, wherein theinput interface is configured to receive the request for the second rideafter the determination of the vehicle to dispatch to the first pickuplocation.
 6. The system according to claim 1, wherein the inputinterface is configured to receive the request for the second ride afterproviding the first pickup indication.
 7. The system according to claim1, wherein the input interface is configured to receive the request forthe second ride after receiving a first pickup arrival indicationindicating the driver arrived at a first pickup location of the firstride.
 8. The system according to claim 1, wherein the processor isconfigured to determine the vehicle to dispatch based at least in parton a determination of a set of vehicles with having routes with delaycriteria for detour from an existing ride.
 9. The system according toclaim 8, wherein the processor is configured to determine the vehicle todispatch based at least in part on a determination of a select vehiclewith a minimum delay time from the set of vehicles within the delaycriteria.
 10. The system according to claim 8, wherein the processor isconfigured to qualify for the delay criteria based at least in part on adetour time from an existing ride.
 11. The system according to claim 1,the processor is configured to determine the vehicle to dispatch basedat least in part on a determination that no other vehicles meets a delaycriteria for detour from an existing ride.
 12. The system according toclaim 11, wherein the processor is configured to determine the vehicleto dispatch based at least in part on assigning a nearest vehicle to thefirst pickup location and wherein the nearest vehicle is not associatedwith a ride from the system.
 13. A method, comprising: receiving, at aninput interface, a ride sharing acceptability indication; determining,using a processor in communication with the input interface, a vehicleto dispatch to the first pickup location for a first ride upon averification of the ride sharing acceptability indication; providing afirst pickup indication to a driver device of the vehicle, wherein thefirst pickup indication indicates to the driver to go to the firstpickup location; receiving, at the input interface, a request for asecond ride; sharing, using the processor, at least a first portion ofthe first ride with at least a second portion of the second ride; andproviding, from the processor to the driver device a second pickupindication for modifying a route from the first pickup indication forthe driver device.
 14. The method according to claim 13, wherein theinput interface is configured to receive a first destination arrivalindication indicating the vehicle arrived at a first destination of thefirst ride.
 15. The method according to claim 13, wherein the vehicle isassociated with a ride from the system prior to the first ride.
 16. Themethod according to claim 13, wherein the determining for the vehicle todispatch is based at least in part on a determination that no othervehicles meets a delay criteria for detour from an existing ride. 17.The method according to claim 13, wherein the receipt of the request forthe second ride, via the input interface, is after the determination ofthe vehicle to dispatch to the first pickup location.
 18. The methodaccording to claim 13, wherein the receipt of the request for the secondride, via the input interface, is after providing the first pickupindication.
 19. The method according to claim 13, wherein the receipt ofthe request for the second ride, via the input interface, is afterreceiving a first pickup arrival indication indicating the vehiclearrived at the first pickup location.
 20. A computer program productembodied in a non-transitory computer readable storage medium andcomprising computer instructions that when executed on a processorconfigures a computer in communication with the processor to: receive,at an input interface, a ride sharing acceptability indication;determine, using the processor in communication with the inputinterface, a vehicle to dispatch to a first pickup location for a firstride upon a verification of the ride sharing acceptability indication;provide a first pickup indication to a driver device of the vehicle,wherein the first pickup indication indicates to the driver to go to thefirst pickup location; receive, at the input interface, a request for asecond ride; share, using the processor, at least a first portion of thefirst ride with at least a second portion of the second ride; andprovide, from the processor to the driver device a second pickupindication for modifying a route from the first pickup indication forthe driver device.